home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Original Shareware 1.1
/
The Original Shareware (WeMake CDs)(Volume 1.1)(CDs, Inc)(1993).iso
/
8
/
ct26.zip
/
CT26.DOC
next >
Wrap
Text File
|
1991-05-24
|
11KB
|
225 lines
Cache Test v 2.6
by
George Spafford
Summary
This program is designed to help a user evaluate the impacts
of a cache, or the changes to an existing cache, on a drive's
performance.
Furthermore, with users' increasingly using caches during a
variety of tasks, it is important to find the optimal cache
settings given the task at hand. Whereas a word processor
might make heavy usage of sequential files, a database
might make heavy usage of random access files. With this
in mind, the memory requirements, sectors cached, write
delays and so forth have many possible variations.
By default, Cache Test creates a 10,000 record sequential file
using 32 byte records and then a 10,000 record random access file
that again uses 32 byte record lengths. Note, even if the default is
changed, any sample string length will be increased by two bytes by
the addition of a CR/LF. You may want to compensate accordingly if
you wish to be exact in your measurements. The sample record size
indicator displays the TRUE sample string size.
This program uses BIOS to do all of its reads and writes,
so any hardware or software cache should be able to get
some good "hits." In attempt to flush caches during the
test, files are frequently opened and closed.
All of the times that this program writes are the result of
subtracting the beginning time from the ending time. Nothing
fancy, so the values are relatively accurate. Note, if you do
some math to compute access times per record, you will run into
the age old problem of significant digits. This program does not
account for any decimal positions. As such, if you try to take the
timings out to 1/10th of a second, the resulting error factor can be
quite high. You will probably notice times when the Total Time does
not equal the summation of the two measured times. This is because
the overall time is on a unique timer and not the other two values
simply added together. (You will also witness this on the test level
where the total time for the random tests does not match the sum of
the individual scores. The same holds true for the sequential tests.)
A few definitions:
"ButterFly Test" The middle record is read and then a
record is alternatingly and read in each
direction from the middle. Say you have
a 100 record file, the read order would
be 50,49,51,48,52,47,53 . . . and so
forth.
"CR/LF" Carriage Return and Line Feed. Decimal 13
and 10 respectively (CHR$(13),CHR$(10)). These
two characters are used as "end of record"
delimitters. As such, they are included in the
byte count when a record is written. If the
sample string is 10 bytes, these two additional
bytes are added to the end resulting in a total
of 12 bytes. Bear this in mind if you want exact
values.
"Crescendo Read" Records are read alternatingly in from the end of
the file and the beginning file. This is to say,
record 1, 10000, 2, 9999, 3, 9998, 4, 9997 etc.
"Random Read/Write" Random functions generate independent random
reads and writes.
"Stepping-by-1" A random access file's records are being accessed
one at a time.
"Stepping-by-10" A random access file's records are being accessed
on every 10th record.
"Write-by-10" A random access file's records are being updated
on every 10th record.
"Overall" This is the total time of all tests AND file
deletes. So, it might not reflect the sum
of all tests exactly, but it should be very
close.
I just wanted to make those meanings a little clearer.
******************************************************************
Usage of this program is:
CT </D:d><F:bbb></N:nnn></S></R></B></?>
CT by itself will clear the screen and then ask you for the
desired drive and then proceed using a 10,000 record
default. It will NOT prompt the user for any other settings.
Explanation of switches:
/D:d This specifies "d" as the drive to be tested.
/F:b This specifies the number of fixed bytes per record.
It must be between 1 and 32,765. The default is 32 bytes.
Use this with the /N:n switch to enhance your testing.
(Because of CR/LF usage in the file structure, the logical
limit for a user input is 32,765 and not the allowable
32,767)
/N:n This specifies the number of test records.
Note, the only limitation here is the available space
on your test drive. You can also go as small as
you want, but you will reach a point where your test
will lose its validity.
The default value, if this switch is not used, is
10,000 records.
/B Test both sequential and random access records.
/R Test random access records only.
/S Test sequential access records only.
Suggestions:
You might want to set up a batch file that purges your cache
before CT is run. This will allow the cache to have a little
fairer test, as opposed to starting out partially full.
Also, if you are interested in the actual hits on your cache, most
cache programs (PC-CACHE and NCACHE for sure) have status switches
that allow you to see the results from the cache's point of view.
The test file is written in the root directory of the target drive.
The file name is TEST$$CT.SPD. If the critter appears, don't panic!
It probably didn't get deleted because of an interrupted test.
HISTORY:
V2.6 5/24/91
I honestly did not intend another update so soon. It was
pointed out to me that the file structure that I had been
using was variable. As such, it made ratio comparisons
somewhat difficult. Now, the default fixed record length
is 32 bytes (the test record count is still 10,000). The
user can specify the record length by using the /F:bbbbb
switch. "bbbbb" must be between 0 and 32,765. Since the
values are now fixed, a user can do a little math (remember
that subject folks??) and discern the records per second and
so forth. Do note, that two bytes are added to the test string
in the files (CR/LF to be exact) that is why the maximum byte
size that a user can specify is 32,765 and not the 32,767 legal
default limit.
V2.5 5/22/91
1. An actual test file byte size field has been added.
This should allow users to track the actual sizes of
the test records being written.
2. Some users suggested that truly random reads and writes
should be added. This serves to get away from any form
of sequentialized data.
3. Again, more cosmetic touchups.
V2.0 5/16/91
Due to some users having limited drive space, switches
were added to allow for different size tests to
occur. I was somewhat hesitant to do this because it
negated the ability to call results "standard," but
what really is standard?
Switches were also added to allow users to select
what tests they want to run. For now, all that can
be specified is whether or not to run all tests,
sequential tests only, or random tests only.
The ButterFly test was also added in an attemp to
give look-ahead caches a hard time. Some of the
caches that use a FIFO method of purging will have a
heck of a time with this one.
Added timers/cleared up timers for the sequential and
overall tests. Also speaking of timers, to avoid
slowing down some routines, I have removed some of
the video effects that were for the user's benefit
only.
Special thanks to Jonathan Fisk for all of his
suggestions and debugging efforts.
Special thanks also go out to Tim Akright, the sysop
of Queued Access for all of his support.
V1.0 5/10/91
Well, I released it. That pretty well sums it up.
I hope this program helps you evaluate some of your problems
or even makes some solutions/benefits clear. This program is
released as shareware. Its price is $5 for each concurrently
used copy. If you have any suggestions or comments, I'd REALLY
like to hear those too.
Sincerely,
George Spafford
3001 LakeShore Drive, #329
St. Joseph, MI 49085
Data: (616) 468-5026 Queued Access BBS 2400-8-N-1
FIDOnet: 1:227/250
And now for the unpleasantries:
CT IS DISTRIBUTED AS IS. THE AUTHOR (GEORGE SPAFFORD) MAKES NO
WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED
TO WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE,
WITH RESPECT TO THIS SOFTWARE AND DOCUMENTATION. IN NO EVENT SHALL
THE AUTHOR BE LIABLE FOR ANY DAMAGES, INCLUDING LOST PROFITS, LOST
SAVINGS, OR ANY OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OF OR THE INABILITY TO USE THIS PROGRAM.
----------------------------------------------------------------